<html><head><title>Agate Rule Tester Help</title>

<link type = "text/css" rel = "stylesheet" href = "main.css">

</head>

<body>

<table width = "80%" border = "0" cellspacing = "0" cellpadding = "2" class = "titlebar">
<tr>
    <td class = "breadcrumbs">
    	<a href = "index.html">Home</a> -&gt; Resources and Notes
    </td>
</tr>
<tr>
	<td class = "title">
		<div id = "sectionTitle">Resources you'll need and points to remember</div>
		<div id = "icon"><img src = "agate48.png"></div>
	</td>
</tr>
</table>

<div id = "content">
<strong>Resources</strong><br>
To do a translation using the Agate Rule Tester, you'll need the following items (which may not be exactly
what you'll end up needing.  This is just what we needed here at The Register)
<ul>
	<li>The Agate Rule Tester</li>
	<li>A raw wire file (one that's come directly from AP before any processing is done to it)</li>
	<li>A formatted InDesign tagged-text file showing the stylization that needs applied.</li>
	<li>A base translation ruleset (if desired)</li>
	<li>Access to PageSpeed</li>
	<li>TextEdit or any other text editor (to open the tagged-text file)</li>
</ul>

<p>
<strong>Notes</strong><br>
The tester is far from perfect.  This is a small list of things to keep in mind while you're 
using it.
<ul>
	<li>Save early and often... I've not learned how to auto-save stuff yet.  Plus,
		there is no "save before quit" option implemented yet, so be careful with
		the command-q stuff.</li>

	<li>To replace a string with nothing, Replace String must be [BLANK] (which it 
		appears is how DT would prefer it).  It makes your rule much more clear to 
		someone else later on anyways.</li>
  
	<li>Newly entered rules are not processed until you click "Run Rules" or toggle
		and existing rule's "Active" checkbox.</li>
	
	<li>Base rules are processed each and every time rules are ran, regardless of what
		translation rules are on or off.</li>
  
	<li>Rules are not processed in real-time as they are moved around.  You must click 
		"Run Rules" once you are happy with the order.</li>
  
	<li>Every save is treated as "save as".  Once loaded, all files are treated
		as existing files that the application has no ties to... meaning that the app
		will always ask you if you want to overwrite a file, regardless of how you
		save.</li>
  
	<li>When saving out the Translation Output, the app will convert DT mnemonics 
		for you if "Show DT Mnemonics" is on.</li>
  
	<li>Spaces ([SP]), while technically a mnemonic, aren't considered as such when
		displaying them as it really messes up the output.</li>
  
	<li>To start a new translation, you must close and reopen the app.  If you
		load the wrong base translation, you must close and reopen the app.  If you 
		load an incorrect sample file, you must close and reopen the app.  (See where
		I'm going with this?)  Yes, I know this sucks.  It's on my list of things to
		fix.</li>
  
	<li>When in doubt, save your translation as it sits, close and reopen the app.
		There are still some rough edges that need worked out.</li>
</ul>

</div>

<div id = "menu">
    <div id = "menuTitle">Help Contents:</div>
	<div id = "menuContents">
		<a href = "index.html">Home</a><br>
		<a href = "introduction.html">Meet the Tester Interface</a><br>
		<a href = "base_translations.html">Creating Base Translations</a><br>
		Resources and Notes<br>
		<a href = "issues_limitations.html">Known Issues/Bugs/Limitations</a>
	</div>
</div>
</body>
</html>
